Physical random access channel (prach) configuration periodicity extension for backhaul links

ABSTRACT

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a wireless communication device may identify a scaling factor associated with determining a periodicity of backhaul physical random access channel (PRACH) resources. The wireless communication device may determine, based at least in part on the scaling factor, the periodicity of the backhaul PRACH resources. The periodicity of the backhaul PRACH resources may be extended as compared to a periodicity of access PRACH resources. Numerous other aspects are provided.

CROSS REFERENCE TO RELATED APPLICATION UNDER 35 U.S.C § 119

This application claims priority to U.S. Provisional Application No.62/695,599, filed on Jul. 9, 2018, entitled “TECHNIQUES AND APPARATUSESFOR PHYSICAL RANDOM ACCESS CHANNEL (PRACH) CONFIGURATION PERIODICITYEXTENSION FOR BACKHAUL LINKS,” U.S. Provisional Application No.62/734,165, filed on Sep. 20, 2018, entitled “PHYSICAL RANDOM ACCESSCHANNEL (PRACH) CONFIGURATION PERIODICITY EXTENSION FOR BACKHAUL LINKS,”U.S. Provisional Application No. 62/791,311, filed on Jan. 11, 2019,entitled “PHYSICAL RANDOM ACCESS CHANNEL (PRACH) CONFIGURATIONPERIODICITY EXTENSION FOR BACKHAUL LINKS,” and U.S. ProvisionalApplication No. 62/806,490, filed on Feb. 15, 2019, entitled “PHYSICALRANDOM ACCESS CHANNEL (PRACH) CONFIGURATION PERIODICITY EXTENSION FORBACKHAUL LINKS,” which are hereby expressly incorporated by referenceherein.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wirelesscommunication, and more particularly to techniques and apparatuses forphysical random access channel (PRACH) configuration periodicityextension for backhaul links.

BACKGROUND

Wireless communication systems are widely deployed to provide varioustelecommunication services such as telephony, video, data, messaging,and broadcasts. Typical wireless communication systems may employmultiple-access technologies capable of supporting communication withmultiple users by sharing available system resources (e.g., bandwidth,transmit power, and/or the like). Examples of such multiple-accesstechnologies include code division multiple access (CDMA) systems, timedivision multiple access (TDMA) systems, frequency-division multipleaccess (FDMA) systems, orthogonal frequency-division multiple access(OFDMA) systems, single-carrier frequency-division multiple access(SC-FDMA) systems, time division synchronous code division multipleaccess (TD-SCDMA) systems, and Long Term Evolution (LTE).LTE/LTE-Advanced is a set of enhancements to the Universal MobileTelecommunications System (UMTS) mobile standard promulgated by theThird Generation Partnership Project (3GPP).

A wireless communication network may include a number of base stations(BSs) that can support communication for a number of user equipment(UEs). A user equipment (UE) may communicate with a base station (BS)via the downlink and uplink. The downlink (or forward link) refers tothe communication link from the BS to the UE, and the uplink (or reverselink) refers to the communication link from the UE to the BS. As will bedescribed in more detail herein, a BS may be referred to as a Node B, agNB, an access point (AP), a radio head, a transmit receive point (TRP),a new radio (NR) BS, a 5G Node B, and/or the like.

The above multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent user equipment to communicate on a municipal, national,regional, and even global level. New radio (NR), which may also bereferred to as 5G, is a set of enhancements to the LTE mobile standardpromulgated by the Third Generation Partnership Project (3GPP). NR isdesigned to better support mobile broadband Internet access by improvingspectral efficiency, lowering costs, improving services, making use ofnew spectrum, and better integrating with other open standards usingorthogonal frequency division multiplexing (OFDM) with a cyclic prefix(CP) (CP-OFDM) on the downlink (DL), using CP-OFDM and/or SC-FDM (e.g.,also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) onthe uplink (UL), as well as supporting beamforming, multiple-inputmultiple-output (MIMO) antenna technology, and carrier aggregation.However, as the demand for mobile broadband access continues toincrease, there exists a need for further improvements in LTE and NRtechnologies. Preferably, these improvements should be applicable toother multiple access technologies and the telecommunication standardsthat employ these technologies.

SUMMARY

In some aspects, a method of wireless communication, performed by a userequipment functionality (UEF) entity, may include identifying a scalingfactor associated with determining a periodicity of backhaul physicalrandom access channel (PRACH) resources; and determining, based at leastin part on the scaling factor, the periodicity of the backhaul PRACHresources, wherein the periodicity of the backhaul PRACH resources isextended as compared to a periodicity of access PRACH resources.

In some aspects, a UEF entity for wireless communication may includememory and one or more processors operatively coupled to the memory. Thememory and the one or more processors may be configured to identify ascaling factor associated with determining a periodicity of backhaulPRACH resources; and determine, based at least in part on the scalingfactor, the periodicity of the backhaul PRACH resources, wherein theperiodicity of the backhaul PRACH resources is extended as compared to aperiodicity of access PRACH resources.

In some aspects, a non-transitory computer-readable medium may store oneor more instructions for wireless communication. The one or moreinstructions, when executed by one or more processors of a UEF entity,may cause the one or more processors to identify a scaling factorassociated with determining a periodicity of backhaul PRACH resources;and determine, based at least in part on the scaling factor, theperiodicity of the backhaul PRACH resources, wherein the periodicity ofthe backhaul PRACH resources is extended as compared to a periodicity ofaccess PRACH resources.

In some aspects, an apparatus for wireless communication may includemeans for identifying a scaling factor associated with determining aperiodicity of backhaul PRACH resources; and means for determining,based at least in part on the scaling factor, the periodicity of thebackhaul PRACH resources, wherein the periodicity of the backhaul PRACHresources is extended as compared to a periodicity of access PRACHresources.

In some aspects, a method of wireless communication, performed by an ANFentity, may include identifying a scaling factor to be used by a UEFentity in association with determining a periodicity of backhaulphysical random access channel (PRACH) resources, wherein theperiodicity of the backhaul PRACH resources is to be extended ascompared to a periodicity of access PRACH resources; and signaling thescaling factor to the UEF entity.

In some aspects, an ANF entity for wireless communication may includememory and one or more processors operatively coupled to the memory. Thememory and the one or more processors may be configured to identify ascaling factor to be used by a UEF entity in association withdetermining a periodicity of backhaul physical random access channel(PRACH) resources, wherein the periodicity of the backhaul PRACHresources is to be extended as compared to a periodicity of access PRACHresources; and signal the scaling factor to the UEF entity.

In some aspects, a non-transitory computer-readable medium may store oneor more instructions for wireless communication. The one or moreinstructions, when executed by one or more processors of an ANF entity,may cause the one or more processors to identify a scaling factor to beused by a UEF entity in association with determining a periodicity ofbackhaul physical random access channel (PRACH) resources, wherein theperiodicity of the backhaul PRACH resources is to be extended ascompared to a periodicity of access PRACH resources; and signal thescaling factor to the UEF entity.

In some aspects, an apparatus for wireless communication may includemeans for identifying a scaling factor to be used by a UEF entity inassociation with determining a periodicity of backhaul physical randomaccess channel (PRACH) resources, wherein the periodicity of thebackhaul PRACH resources is to be extended as compared to a periodicityof access PRACH resources; and means for signaling the scaling factor tothe UEF entity.

In some aspects, a method of wireless communication, performed by anaccess node functionality (ANF) entity, may include configuring a timeoffset of backhaul physical random access channel (PRACH) resources; andtransmitting information that identifies the time offset, wherein thetime offset is different from a time offset that is identified based atleast in part on a PRACH configuration index.

In some aspects, an ANF entity for wireless communication may includememory and one or more processors operatively coupled to the memory. Thememory and the one or more processors may be configured to configure atime offset of backhaul physical random access channel (PRACH)resources; and transmit information that identifies the time offset,wherein the time offset is different from a time offset that isidentified based at least in part on a PRACH configuration index.

In some aspects, a non-transitory computer-readable medium may store oneor more instructions for wireless communication. The one or moreinstructions, when executed by one or more processors of an ANF entity,may cause the one or more processors to configure a time offset ofbackhaul physical random access channel (PRACH) resources; and transmitinformation that identifies the time offset, wherein the time offset isdifferent from a time offset that is identified based at least in parton a PRACH configuration index.

In some aspects, an apparatus for wireless communication may includemeans for configuring a time offset of backhaul physical random accesschannel (PRACH) resources; and means for transmitting information thatidentifies the time offset, wherein the time offset is different from atime offset that is identified based at least in part on a PRACHconfiguration index.

In some aspects, a method of wireless communication, performed by a UEFentity, may include receiving information that identifies a time offsetassociated with backhaul physical random access channel (PRACH)resources, wherein the time offset is different from a time offset thatis identified based at least in part on a PRACH configuration index;identifying a set of backhaul PRACH resources based at least in part onthe time offset; and transmitting a RACH transmission using theidentified set of back backhaul PRACH resources.

In some aspects, a UEF entity for wireless communication may includememory and one or more processors operatively coupled to the memory. Thememory and the one or more processors may be configured to receiveinformation that identifies a time offset associated with backhaulphysical random access channel (PRACH) resources, wherein the timeoffset is different from a time offset that is identified based at leastin part on a PRACH configuration index; identify a set of backhaul PRACHresources based at least in part on the time offset; and transmit a RACHtransmission using the identified set of back backhaul PRACH resources.

In some aspects, a non-transitory computer-readable medium may store oneor more instructions for wireless communication. The one or moreinstructions, when executed by one or more processors of a UEF entity,may cause the one or more processors to receive information thatidentifies a time offset associated with backhaul physical random accesschannel (PRACH) resources, wherein the time offset is different from atime offset that is identified based at least in part on a PRACHconfiguration index; identify a set of backhaul PRACH resources based atleast in part on the time offset; and transmit a RACH transmission usingthe identified set of back backhaul PRACH resources.

In some aspects, an apparatus for wireless communication may includemeans for receiving information that identifies a time offset associatedwith backhaul physical random access channel (PRACH) resource, whereinthe time offset is different from a time offset that is identified basedat least in part on a PRACH configuration index s; means for identifyinga set of backhaul PRACH resources based at least in part on the timeoffset; and means for transmitting a RACH transmission using theidentified set of back backhaul PRACH resources.

Aspects generally include a method, apparatus, system, computer programproduct, non-transitory computer-readable medium, user equipment, basestation, wireless communication device, and processing system assubstantially described herein with reference to and as illustrated bythe accompanying drawings, specification, and appendices.

The foregoing has outlined rather broadly the features and technicaladvantages of examples according to the disclosure in order that thedetailed description that follows may be better understood. Additionalfeatures and advantages will be described hereinafter. The conceptionand specific examples disclosed may be readily utilized as a basis formodifying or designing other structures for carrying out the samepurposes of the present disclosure. Such equivalent constructions do notdepart from the scope of the appended claims. Characteristics of theconcepts disclosed herein, both their organization and method ofoperation, together with associated advantages will be better understoodfrom the following description when considered in connection with theaccompanying figures. Each of the figures is provided for the purpose ofillustration and description, and not as a definition of the limits ofthe claims.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above-recited features of the presentdisclosure can be understood in detail, a more particular description,briefly summarized above, may be had by reference to aspects, some ofwhich are illustrated in the appended drawings. It is to be noted,however, that the appended drawings illustrate only certain typicalaspects of this disclosure and are therefore not to be consideredlimiting of its scope, for the description may admit to other equallyeffective aspects. The same reference numbers in different drawings mayidentify the same or similar elements.

FIG. 1 is a block diagram conceptually illustrating an example of awireless communication network, in accordance with various aspects ofthe present disclosure.

FIG. 2 is a block diagram conceptually illustrating an example of a basestation in communication with a user equipment (UE) in a wirelesscommunication network, in accordance with various aspects of the presentdisclosure.

FIG. 3A is a block diagram conceptually illustrating an example of aframe structure in a wireless communication network, in accordance withvarious aspects of the present disclosure.

FIG. 3B is a block diagram conceptually illustrating an examplesynchronization communication hierarchy in a wireless communicationnetwork, in accordance with various aspects of the present disclosure.

FIG. 4 is a block diagram conceptually illustrating an example slotformat with a normal cyclic prefix, in accordance with various aspectsof the present disclosure.

FIG. 5 is a diagram illustrating examples of radio access networks, inaccordance with various aspects of the present disclosure.

FIG. 6 is a diagram illustrating an example of resource partitioning ina wireless backhaul network, in accordance with various aspects of thepresent disclosure.

FIG. 7 is a diagram illustrating an example of determining a periodicityand a time offset of backhaul physical RACH resources, in accordancewith various aspects of the present disclosure.

FIG. 8 is a diagram illustrating an example process performed, forexample, by a user equipment functionality (UEF) entity, in accordancewith various aspects of the present disclosure.

FIG. 9 is a diagram illustrating an example process performed, forexample, by an access node functionality (ANF) entity, in accordancewith various aspects of the present disclosure.

FIG. 10 is a diagram illustrating an example process performed, forexample, by an ANF entity, in accordance with various aspects of thepresent disclosure.

FIG. 11 is a diagram illustrating an example process performed, forexample, by a UEF entity, in accordance with various aspects of thepresent disclosure.

DETAILED DESCRIPTION

Various aspects of the disclosure are described more fully hereinafterwith reference to the accompanying drawings. This disclosure may,however, be embodied in many different forms and should not be construedas limited to any specific structure or function presented throughoutthis disclosure. Rather, these aspects are provided so that thisdisclosure will be thorough and complete, and will fully convey thescope of the disclosure to those skilled in the art. Based on theteachings herein one skilled in the art should appreciate that the scopeof the disclosure is intended to cover any aspect of the disclosuredisclosed herein, whether implemented independently of or combined withany other aspect of the disclosure. For example, an apparatus may beimplemented or a method may be practiced using any number of the aspectsset forth herein. In addition, the scope of the disclosure is intendedto cover such an apparatus or method which is practiced using otherstructure, functionality, or structure and functionality in addition toor other than the various aspects of the disclosure set forth herein. Itshould be understood that any aspect of the disclosure disclosed hereinmay be embodied by one or more elements of a claim.

Several aspects of telecommunication systems will now be presented withreference to various apparatuses and techniques. These apparatuses andtechniques will be described in the following detailed description andillustrated in the accompanying drawings by various blocks, modules,components, circuits, steps, processes, algorithms, and/or the like(collectively referred to as “elements”). These elements may beimplemented using hardware, software, or combinations thereof. Whethersuch elements are implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem.

It is noted that while aspects may be described herein using terminologycommonly associated with 3G and/or 4G wireless technologies, aspects ofthe present disclosure can be applied in other generation-basedcommunication systems, such as 5G and later, including NR technologies.

FIG. 1 is a diagram illustrating a network 100 in which aspects of thepresent disclosure may be practiced. The network 100 may be an LTEnetwork or some other wireless network, such as a 5G or NR network.Wireless network 100 may include a number of BSs 110 (shown as BS 110 a,BS 110 b, BS 110 c, and BS 110 d) and other network entities. A BS is anentity that communicates with user equipment (UEs) and may also bereferred to as a base station, a NR BS, a Node B, a gNB, a 5G node B(NB), an access point, a transmit receive point (TRP), and/or the like.Each BS may provide communication coverage for a particular geographicarea. In 3GPP, the term “cell” can refer to a coverage area of a BSand/or a BS subsystem serving this coverage area, depending on thecontext in which the term is used.

A BS may provide communication coverage for a macro cell, a pico cell, afemto cell, and/or another type of cell. A macro cell may cover arelatively large geographic area (e.g., several kilometers in radius)and may allow unrestricted access by UEs with service subscription. Apico cell may cover a relatively small geographic area and may allowunrestricted access by UEs with service subscription. A femto cell maycover a relatively small geographic area (e.g., a home) and may allowrestricted access by UEs having association with the femto cell (e.g.,UEs in a closed subscriber group (CSG)). ABS for a macro cell may bereferred to as a macro BS. ABS for a pico cell may be referred to as apico BS. A BS for a femto cell may be referred to as a femto BS or ahome BS. In the example shown in FIG. 1, a BS 110 a may be a macro BSfor a macro cell 102 a, a BS 110 b may be a pico BS for a pico cell 102b, and a BS 110 c may be a femto BS for a femto cell 102 c. A BS maysupport one or multiple (e.g., three) cells. The terms “eNB”, “basestation”, “NR BS”, “gNB”, “TRP”, “AP”, “node B”, “5G NB”, and “cell” maybe used interchangeably herein.

In some aspects, a cell may not necessarily be stationary, and thegeographic area of the cell may move according to the location of amobile BS. In some aspects, the BSs may be interconnected to one anotherand/or to one or more other BSs or network nodes (not shown) in theaccess network 100 through various types of backhaul interfaces such asa direct physical connection, a virtual network, and/or the like usingany suitable transport network.

Wireless network 100 may also include relay stations. A relay station isan entity that can receive a transmission of data from an upstreamstation (e.g., a BS or a UE) and send a transmission of the data to adownstream station (e.g., a UE or a BS). A relay station may also be aUE that can relay transmissions for other UEs. In the example shown inFIG. 1, a relay station 110 d may communicate with macro BS 110 a and aUE 120 d in order to facilitate communication between BS 110 a and UE120 d. A relay station may also be referred to as a relay BS, a relaybase station, a relay, and/or the like.

Wireless network 100 may be a heterogeneous network that includes BSs ofdifferent types, e.g., macro BSs, pico BSs, femto BSs, relay BSs, and/orthe like. These different types of BSs may have different transmit powerlevels, different coverage areas, and different impact on interferencein wireless network 100. For example, macro BSs may have a high transmitpower level (e.g., 5 to 40 Watts) whereas pico BSs, femto BSs, and relayBSs may have lower transmit power levels (e.g., 0.1 to 2 Watts).

A network controller 130 may couple to a set of BSs and may providecoordination and control for these BSs. Network controller 130 maycommunicate with the BSs via a backhaul. The BSs may also communicatewith one another, e.g., directly or indirectly via a wireless orwireline backhaul.

UEs 120 (e.g., 120 a, 120 b, 120 c) may be dispersed throughout wirelessnetwork 100, and each UE may be stationary or mobile. A UE may also bereferred to as an access terminal, a terminal, a mobile station, asubscriber unit, a station, and/or the like. A UE may be a cellularphone (e.g., a smart phone), a personal digital assistant (PDA), awireless modem, a wireless communication device, a handheld device, alaptop computer, a cordless phone, a wireless local loop (WLL) station,a tablet, a camera, a gaming device, a netbook, a smartbook, anultrabook, medical device or equipment, biometric sensors/devices,wearable devices (smart watches, smart clothing, smart glasses, smartwrist bands, smart jewelry (e.g., smart ring, smart bracelet)), anentertainment device (e.g., a music or video device, or a satelliteradio), a vehicular component or sensor, smart meters/sensors,industrial manufacturing equipment, a global positioning system device,or any other suitable device that is configured to communicate via awireless or wired medium.

Some UEs may be considered machine-type communication (MTC) or evolvedor enhanced machine-type communication (eMTC) UEs. MTC and eMTC UEsinclude, for example, robots, drones, remote devices, such as sensors,meters, monitors, location tags, and/or the like, that may communicatewith a base station, another device (e.g., remote device), or some otherentity. A wireless node may provide, for example, connectivity for or toa network (e.g., a wide area network such as Internet or a cellularnetwork) via a wired or wireless communication link. Some UEs may beconsidered Internet-of-Things (IoT) devices, and/or may be implementedas may be implemented as NB-IoT (narrowband internet of things) devices.Some UEs may be considered a Customer Premises Equipment (CPE). UE 120may be included inside a housing that houses components of UE 120, suchas processor components, memory components, and/or the like.

In general, any number of wireless networks may be deployed in a givengeographic area. Each wireless network may support a particular RAT andmay operate on one or more frequencies. A RAT may also be referred to asa radio technology, an air interface, and/or the like. A frequency mayalso be referred to as a carrier, a frequency channel, and/or the like.Each frequency may support a single RAT in a given geographic area inorder to avoid interference between wireless networks of different RATs.In some cases, NR or 5G RAT networks may be deployed.

In some aspects, two or more UEs 120 (e.g., shown as UE 120 a and UE 120e) may communicate directly using one or more sidelink channels (e.g.,without using a base station 110 as an intermediary to communicate withone another). For example, the UEs 120 may communicate usingpeer-to-peer (P2P) communications, device-to-device (D2D)communications, a vehicle-to-everything (V2X) protocol (e.g., which mayinclude a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure(V2I) protocol, and/or the like), a mesh network, and/or the like. Inthis case, the UE 120 may perform scheduling operations, resourceselection operations, and/or other operations described elsewhere hereinas being performed by the base station 110.

As indicated above, FIG. 1 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 1.

FIG. 2 shows a block diagram of a design 200 of base station 110 and UE120, which may be one of the base stations and one of the UEs in FIG. 1.Base station 110 may be equipped with T antennas 234 a through 234 t,and UE 120 may be equipped with R antennas 252 a through 252 r, where ingeneral T≥1 and R≥1.

At base station 110, a transmit processor 220 may receive data from adata source 212 for one or more UEs, select one or more modulation andcoding schemes (MCS) for each UE based at least in part on channelquality indicators (CQIs) received from the UE, process (e.g., encodeand modulate) the data for each UE based at least in part on the MCS(s)selected for the UE, and provide data symbols for all UEs. Transmitprocessor 220 may also process system information (e.g., for semi-staticresource partitioning information (SRPI) and/or the like) and controlinformation (e.g., CQI requests, grants, upper layer signaling, and/orthe like) and provide overhead symbols and control symbols. Transmitprocessor 220 may also generate reference symbols for reference signals(e.g., the cell-specific reference signal (CRS)) and synchronizationsignals (e.g., the primary synchronization signal (PSS) and secondarysynchronization signal (SSS)). A transmit (TX) multiple-inputmultiple-output (MIMO) processor 230 may perform spatial processing(e.g., precoding) on the data symbols, the control symbols, the overheadsymbols, and/or the reference symbols, if applicable, and may provide Toutput symbol streams to T modulators (MODs) 232 a through 232 t. Eachmodulator 232 may process a respective output symbol stream (e.g., forOFDM and/or the like) to obtain an output sample stream. Each modulator232 may further process (e.g., convert to analog, amplify, filter, andupconvert) the output sample stream to obtain a downlink signal. Tdownlink signals from modulators 232 a through 232 t may be transmittedvia T antennas 234 a through 234 t, respectively. According to variousaspects described in more detail below, the synchronization signals canbe generated with location encoding to convey additional information.

At UE 120, antennas 252 a through 252 r may receive the downlink signalsfrom base station 110 and/or other base stations and may providereceived signals to demodulators (DEMODs) 254 a through 254 r,respectively. Each demodulator 254 may condition (e.g., filter, amplify,downconvert, and digitize) a received signal to obtain input samples.Each demodulator 254 may further process the input samples (e.g., forOFDM and/or the like) to obtain received symbols. A MIMO detector 256may obtain received symbols from all R demodulators 254 a through 254 r,perform MIMO detection on the received symbols if applicable, andprovide detected symbols. A receive processor 258 may process (e.g.,demodulate and decode) the detected symbols, provide decoded data for UE120 to a data sink 260, and provide decoded control information andsystem information to a controller/processor 280. A channel processormay determine reference signal received power (RSRP), received signalstrength indicator (RSSI), reference signal received quality (RSRQ),channel quality indicator (CQI), and/or the like. In some aspects, oneor more components of UE 120 may be included in a housing.

On the uplink, at UE 120, a transmit processor 264 may receive andprocess data from a data source 262 and control information (e.g., forreports comprising RSRP, RSSI, RSRQ, CQI, and/or the like) fromcontroller/processor 280. Transmit processor 264 may also generatereference symbols for one or more reference signals. The symbols fromtransmit processor 264 may be precoded by a TX MIMO processor 266 ifapplicable, further processed by modulators 254 a through 254 r (e.g.,for DFT-s-OFDM, CP-OFDM, and/or the like), and transmitted to basestation 110. At base station 110, the uplink signals from UE 120 andother UEs may be received by antennas 234, processed by demodulators232, detected by a MIMO detector 236 if applicable, and furtherprocessed by a receive processor 238 to obtain decoded data and controlinformation sent by UE 120. Receive processor 238 may provide thedecoded data to a data sink 239 and the decoded control information tocontroller/processor 240. Base station 110 may include communicationunit 244 and communicate to network controller 130 via communicationunit 244. Network controller 130 may include communication unit 294,controller/processor 290, and memory 292.

Controller/processor 240 of base station 110, controller/processor 280of UE 120, and/or any other component(s) of FIG. 2 may perform one ormore techniques associated with physical random access channel (PRACH)configuration periodicity extension for backhaul links, as described inmore detail elsewhere herein. For example, controller/processor 240 ofbase station 110, controller/processor 280 of UE 120, and/or any othercomponent(s) of FIG. 2 may perform or direct operations of, for example,process 800 of FIG. 8, process 900 of FIG. 9, process 1000 of FIG. 10,process 1100 of FIG. 11, and/or other processes as described herein.Memories 242 and 282 may store data and program codes for base station110 and UE 120, respectively. A scheduler 246 may schedule UEs for datatransmission on the downlink and/or uplink.

In some aspects, base station 110 (e.g., a base station that operateswith UE functionality (UEF)) may include means for identifying a scalingfactor associated with determining a periodicity of backhaul PRACHresources; means for determining, based at least in part on the scalingfactor, the periodicity of the backhaul PRACH resources, wherein theperiodicity of the backhaul PRACH resources is extended as compared to aperiodicity of access PRACH resources; and/or the like. In some aspects,such means may include one or more components of base station 110described in connection with FIG. 2.

In some aspects, a base station 110 (e.g., a base station that operateswith access node functionality (ANF)) may include means for identifyinga scaling factor to be used by a UEF entity (e.g., a base station 110with UEF) in association with determining a periodicity of backhaulPRACH resources, wherein the periodicity of the backhaul PRACH resourcesis to be extended as compared to a periodicity of access PRACHresources; means for signaling the scaling factor to the UEF entity;and/or the like. In some aspects, such means may include one or morecomponents of base station 110 described in connection with FIG. 2.

In some aspects, a base station 110 (e.g., a base station 110 thatoperates with ANF) may include means for configuring a time offset ofbackhaul PRACH resources; means for transmitting information thatidentifies the offset, wherein the time offset is different from a timeoffset that is identified based at least in part on a PRACHconfiguration index; and/or the like. In some aspects, such means mayinclude one or more components of base station 110 described inconnection with FIG. 2.

In some aspects, a base station 110 (e.g., a base station 110 thatoperates with UEF) may include means for receiving information thatidentifies a time offset associated with backhaul PRACH resources,wherein the time offset is different from a time offset that isidentified based at least in part on a PRACH configuration index; meansfor identifying a set of backhaul PRACH resources based at least in parton the time offset; means for transmitting a RACH transmission using theidentified set of backhaul PRACH resources; and/or the like. In someaspects, such means may include one or more components of base station110 described in connection with FIG. 2.

As indicated above, FIG. 2 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 2.

FIG. 3A shows an example frame structure 300 for FDD in atelecommunications system (e.g., NR). The transmission timeline for eachof the downlink and uplink may be partitioned into units of radio frames(sometimes referred to as frames). Each radio frame may have apredetermined duration (e.g., 10 milliseconds (ms)) and may bepartitioned into a set of Z (Z≥1) subframes (e.g., with indices of 0through Z−1). Each subframe may have a predetermined duration (e.g., 1ms) and may include a set of slots (e.g., 2^(m) slots per subframe areshown in FIG. 3A, where m is a numerology used for a transmission, suchas 0, 1, 2, 3, 4, and/or the like). Each slot may include a set of Lsymbol periods. For example, each slot may include fourteen symbolperiods (e.g., as shown in FIG. 3A), seven symbol periods, or anothernumber of symbol periods. In a case where the subframe includes twoslots (e.g., when m=1), the subframe may include 2L symbol periods,where the 2L symbol periods in each subframe may be assigned indices of0 through 2L-1. In some aspects, a scheduling unit for the FDD mayframe-based, subframe-based, slot-based, symbol-based, and/or the like.

While some techniques are described herein in connection with frames,subframes, slots, and/or the like, these techniques may equally apply toother types of wireless communication structures, which may be referredto using terms other than “frame,” “subframe,” “slot,” and/or the likein 5G NR. In some aspects, a wireless communication structure may referto a periodic time-bounded communication unit defined by a wirelesscommunication standard and/or protocol. Additionally, or alternatively,different configurations of wireless communication structures than thoseshown in FIG. 3A may be used.

In certain telecommunications (e.g., NR), a base station may transmitsynchronization signals. For example, a base station may transmit aprimary synchronization signal (PSS), a secondary synchronization signal(SSS), and/or the like, on the downlink for each cell supported by thebase station. The PSS and SSS may be used by UEs for cell search andacquisition. For example, the PSS may be used by UEs to determine symboltiming, and the SSS may be used by UEs to determine a physical cellidentifier, associated with the base station, and frame timing. The basestation may also transmit a physical broadcast channel (PBCH). The PBCHmay carry some system information, such as system information thatsupports initial access by UEs.

In some aspects, the base station may transmit the PSS, the SSS, and/orthe PBCH in accordance with a synchronization communication hierarchy(e.g., a synchronization signal (SS) hierarchy) including multiplesynchronization communications (e.g., SS blocks), as described below inconnection with FIG. 3B.

FIG. 3B is a block diagram conceptually illustrating an example SShierarchy, which is an example of a synchronization communicationhierarchy. As shown in FIG. 3B, the SS hierarchy may include an SS burstset, which may include a plurality of SS bursts (identified as SS burst0 through SS burst B-1, where B is a maximum number of repetitions ofthe SS burst that may be transmitted by the base station). As furthershown, each SS burst may include one or more SS blocks (identified as SSblock 0 through SS block (b_(max_SS-1)), where b_(max_SS-1) is a maximumnumber of SS blocks that can be carried by an SS burst). In someaspects, different SS blocks may be beam-formed differently. An SS burstset may be periodically transmitted by a wireless node, such as every Xmilliseconds, as shown in FIG. 3B. In some aspects, an SS burst set mayhave a fixed or dynamic length, shown as Y milliseconds in FIG. 3B.

The SS burst set shown in FIG. 3B is an example of a synchronizationcommunication set, and other synchronization communication sets may beused in connection with the techniques described herein. Furthermore,the SS block shown in FIG. 3B is an example of a synchronizationcommunication, and other synchronization communications may be used inconnection with the techniques described herein.

In some aspects, an SS block includes resources that carry the PSS, theSSS, the PBCH, and/or other synchronization signals (e.g., a tertiarysynchronization signal (TSS)) and/or synchronization channels. In someaspects, multiple SS blocks are included in an SS burst, and the PSS,the SSS, and/or the PBCH may be the same across each SS block of the SSburst. In some aspects, a single SS block may be included in an SSburst. In some aspects, the SS block may be at least four symbol periodsin length, where each symbol carries one or more of the PSS (e.g.,occupying one symbol), the SSS (e.g., occupying one symbol), and/or thePBCH (e.g., occupying two symbols).

In some aspects, the symbols of an SS block are consecutive, as shown inFIG. 3B. In some aspects, the symbols of an SS block arenon-consecutive. Similarly, in some aspects, one or more SS blocks ofthe SS burst may be transmitted in consecutive radio resources (e.g.,consecutive symbol periods) during one or more slots. Additionally, oralternatively, one or more SS blocks of the SS burst may be transmittedin non-consecutive radio resources.

In some aspects, the SS bursts may have a burst period, whereby the SSblocks of the SS burst are transmitted by the base station according tothe burst period. In other words, the SS blocks may be repeated duringeach SS burst. In some aspects, the SS burst set may have a burst setperiodicity, whereby the SS bursts of the SS burst set are transmittedby the base station according to the fixed burst set periodicity. Inother words, the SS bursts may be repeated during each SS burst set.

The base station may transmit system information, such as systeminformation blocks (SIBs) on a physical downlink shared channel (PDSCH)in certain slots. The base station may transmit control information/dataon a physical downlink control channel (PDCCH) in C symbol periods of aslot, where B may be configurable for each slot. The base station maytransmit traffic data and/or other data on the PDSCH in the remainingsymbol periods of each slot.

As indicated above, FIGS. 3A and 3B are provided as examples. Otherexamples are possible and may differ from what was described with regardto FIGS. 3A and 3B.

FIG. 4 shows an example slot format 410 with a normal cyclic prefix. Theavailable time frequency resources may be partitioned into resourceblocks. Each resource block may cover a set to of subcarriers (e.g., 12subcarriers) in one slot and may include a number of resource elements.Each resource element may cover one subcarrier in one symbol period(e.g., in time) and may be used to send one modulation symbol, which maybe a real or complex value.

An interlace structure may be used for each of the downlink and uplinkfor FDD in certain telecommunications systems (e.g., NR). For example, Qinterlaces with indices of 0 through Q−1 may be defined, where Q may beequal to 4, 6, 8, 10, or some other value. Each interlace may includeslots that are spaced apart by Q frames. In particular, interlace q mayinclude slots q, q+Q, q+2Q, etc., where qϵ{0, . . . , Q−1}.

A UE may be located within the coverage of multiple BSs. One of theseBSs may be selected to serve the UE. The serving BS may be selectedbased at least in part on various criteria such as received signalstrength, received signal quality, path loss, and/or the like. Receivedsignal quality may be quantified by a signal-to-noise-and-interferenceratio (SINR), or a reference signal received quality (RSRQ), or someother metric. The UE may operate in a dominant interference scenario inwhich the UE may observe high interference from one or more interferingBSs.

While aspects of the examples described herein may be associated with NRor 5G technologies, aspects of the present disclosure may be applicablewith other wireless communication systems. New radio (NR) may refer toradios configured to operate according to a new air interface (e.g.,other than Orthogonal Frequency Divisional Multiple Access (OFDMA)-basedair interfaces) or fixed transport layer (e.g., other than InternetProtocol (IP)). In aspects, NR may utilize OFDM with a CP (hereinreferred to as cyclic prefix OFDM or CP-OFDM) and/or SC-FDM on theuplink, may utilize CP-OFDM on the downlink and include support forhalf-duplex operation using TDD. In aspects, NR may, for example,utilize OFDM with a CP (herein referred to as CP-OFDM) and/or discreteFourier transform spread orthogonal frequency-division multiplexing(DFT-s-OFDM) on the uplink, may utilize CP-OFDM on the downlink andinclude support for half-duplex operation using TDD. NR may includeEnhanced Mobile Broadband (eMBB) service targeting wide bandwidth (e.g.,80 megahertz (MHz) and beyond), millimeter wave (mmW) targeting highcarrier frequency (e.g., 60 gigahertz (GHz)), massive MTC (mMTC)targeting non-backward compatible MTC techniques, and/or missioncritical targeting ultra reliable low latency communications (URLLC)service.

In some aspects, a single component carrier bandwidth of 100 MHZ may besupported. NR resource blocks may span 12 sub-carriers with asub-carrier bandwidth of 60 or 120 kilohertz (kHz) over a 0.1millisecond (ms) duration. Each radio frame may include 40 slots and mayhave a length of 10 ms. Consequently, each slot may have a length of0.25 ms. Each slot may indicate a link direction (e.g., DL or UL) fordata transmission and the link direction for each slot may bedynamically switched. Each slot may include DL/UL data as well as DL/ULcontrol data.

Beamforming may be supported and beam direction may be dynamicallyconfigured. MIMO transmissions with precoding may also be supported.MIMO configurations in the DL may support up to 8 transmit antennas withmulti-layer DL transmissions up to 8 streams and up to 2 streams per UE.Multi-layer transmissions with up to 2 streams per UE may be supported.Aggregation of multiple cells may be supported with up to 8 servingcells. Alternatively, NR may support a different air interface, otherthan an OFDM-based interface. NR networks may include entities suchcentral units or distributed units.

As indicated above, FIG. 4 is provided as an example. Other examples arepossible and may differ from what was described with regard to FIG. 4.

FIG. 5 is a diagram illustrating examples 500 of radio access networks,in accordance with various aspects of the disclosure.

As shown by reference number 505, a traditional (e.g., 3G, 4G, LTE,etc.) radio access network may include multiple base stations 510 (e.g.,access nodes (AN)), where each base station 510 communicates with a corenetwork via a wired backhaul link 515, such as a fiber connection. Abase station 510 may communicate with a UE 520 via an access link 525,which may be a wireless link. In some aspects, a base station 510 shownin FIG. 5 may correspond to a base station 110 shown in FIG. 1.Similarly, a UE 520 shown in FIG. 5 may correspond to a UE 120 shown inFIG. 1.

As shown by reference number 530, a radio access network may include awireless backhaul network, where at least one base station is an anchorbase station 535 that communicates with a core network via a wiredbackhaul link 540, such as a fiber connection. The wireless backhaulnetwork may include one or more non-anchor base stations 545 thatcommunicate directly with or indirectly with (e.g., via one or morenon-anchor base stations 545) the anchor base station 535 via one ormore backhaul links 550 to form a backhaul path to the core network forcarrying backhaul traffic. Backhaul link 550 may be a wireless link.Anchor base station(s) 535 and/or non-anchor base station(s) 545 maycommunicate with one or more UEs 555 via access links 560, which may bewireless links for carrying access traffic. In some aspects, an anchorbase station 535 and/or a non-anchor base station 545 shown in FIG. 5may correspond to a base station 110 shown in FIG. 1. Similarly, a UE555 shown in FIG. 5 may correspond to a UE 120 shown in FIG. 1.

As shown by reference number 565, in some aspects, a radio accessnetwork that includes a wireless backhaul network may utilize millimeterwave technology and/or directional communications (e.g., beamforming,precoding, and/or the like) for communications between base stationsand/or UEs (e.g., between two base stations, between two UEs, and/orbetween a base station and a UE). For example, the wireless backhaullinks 570 between base stations may use millimeter waves to carryinformation and/or may be directed toward a target base station usingbeamforming, precoding, and/or the like. Similarly, the wireless accesslinks 575 between a UE and a base station may use millimeter wavesand/or may be directed toward a target wireless node (e.g., a UE and/ora base station). In this way, inter-link interference may be reduced.

As indicated above, FIG. 5 is provided as an example. Other examples arepossible and may differ from what was described with regard to FIG. 5.

FIG. 6 is a diagram illustrating an example 600 of resource partitioningin a wireless backhaul network, in accordance with various aspects ofthe disclosure.

As shown in FIG. 6, an anchor base station 605 may be connected to acore network 610 via a wired backhaul link 615, such as a fiberconnection. As further shown, non-anchor base stations 620 maycommunicate directly with anchor base station 605 via wireless backhaullinks 625. In some aspects, one or more non-anchor base stations maycommunicate indirectly with anchor base station 605 via multiplewireless backhaul links (e.g., via one or more other non-anchor basestations). For example, and as shown, a first set of non-anchor basestations 630 may communicate indirectly with anchor base station 605 viaa wireless backhaul link 635 and a wireless backhaul link 625. Asfurther shown, a second set of non-anchor base stations 640 maycommunicate indirectly with anchor base station 605 via a wirelessbackhaul link 645, a wireless backhaul link 635, and a wireless backhaullink 625.

As further shown, a UE 650 may communicate with anchor base station 605via a wireless access link 655, a UE 660 may communicate with anon-anchor base station 620 via a wireless access link 665, and a UE 670may communicate with a non- anchor base station 630 via a wirelessaccess link 675.

In some aspects, an index (e.g., a color index) may be assigned to awireless link and/or a wireless node (e.g., a base station or a UE). Theindex may indicate one or more resources allocated to a wireless nodefor communication via the wireless link. For example, and as shown, afirst index 680 may be associated with transmission time intervals(TTIs) 0, 2, and 4, and a second index 685 may be associated with TTIs 1and 3. As indicated by light gray lines in FIG. 6, the first index 680may be assigned to wireless backhaul links 625 and 645 and wirelessaccess links 655 and 675. Thus, information may be transmitted overthese links during TTIs 0, 2, and 4, and not during TTIs 1 and 3.Similarly, and as indicated by dark gray lines in FIG. 6, the secondindex 685 may be assigned to wireless backhaul links 635 and wirelessaccess links 665. Thus, information may be transmitted over these linksduring TTIs 1 and 3, and not during TTIs 0, 2, and 4. In this way,wireless nodes may coordinate communication such that a wireless node isnot configured to transmit and receive data at the same time.

While the resources are shown as time resources, additionally, oralternatively, an index may be associated with a frequency resource.Furthermore, the configuration of base stations and UEs in FIG. 6 isshown as an example, and other examples are possible.

As indicated above, FIG. 6 is provided as an example. Other examples arepossible and may differ from what was described with regard to FIG. 6.

In an integrated access and backhaul (IAB) network, such as thosedescribed in association with FIGS. 5 and 6, a base station is typicallyconnected, via a wireless backhaul link, to a nearest neighbor basestation. However, in some cases, the base station may need to connect toa base station that is a comparatively further distance away than thenearest neighbor base station (e.g., for load balancing in a scenariowhere the nearest neighbor base station is using an amount of resourcesfor access transmissions such that the nearest neighbor base stationcannot transport backhaul transmissions). Thus, backhaul random accesschannel (RACH) design may need to support different (e.g., higher) roundtrip times and link gains as compared to access RACH design.

Further, in the IAB network, a given base station may receive bothbackhaul RACH transmissions and access RACH transmissions. In somecases, differences between link gains of backhaul RACH and access RACHmay exist. Such differences may result from, for example, differentnumbers of transmit antennas used for backhaul RACH as compared toaccess RACH, different transmission powers used for backhaul RACH ascompared to access RACH, different amounts of hand and/or body lossexperienced by backhaul RACH as compared to access RACH, different pathlosses experienced by backhaul RACH as compared to access RACH, and/orthe like.

Additionally, a number of supported cyclic shifts for each Zadoff-Chu(ZC) root sequence associated with RACH transmission should be designedsuch that a gap between neighbouring cyclic shifts can handle a desiredround trip distance. For example, assume that an IAB network is to bedesigned such that base stations that are separated by M (M≥1) hops areto be able to transmit RACH to one another. In order to handle such acase, a number of supported cyclic shifts for each ZC root sequence inbackhaul RACH is [1/(2×M)]th of that of access RACH. As a particularexample, if an IAB network is to be designed such that base stationsthat are separated by 3 hops are to be able to transmit RACH to oneanother, then a number of supported cyclic shifts for each ZC rootsequence in backhaul RACH is ⅙th (e.g., 1/(2×3)=⅙th) of that of accessRACH. Hence, if access links and backhaul links use the sametime-frequency resources for RACH transmission, supportable cyclicshifts for RACH transmission decrease significantly. This requires theIAB network to use more ZC root sequences in order to support a givennumber of RACH preambles (e.g., 64 RACH preambles) in one RACH occasion,which causes higher interference across RACH transmissions inneighbouring cells.

This also leads to a trade-off when the IAB network configures accessRACH preambles and backhaul RACH preambles in the same time-frequencyresources. For example, if the network configures RACH preamble formatB4 (e.g., with 12 repetitions and a 3.8 microsecond (μs) cyclic prefixduration with 120 kilohertz (kHz) subcarrier spacing (SCS)) in order tosatisfy an access link budget requirement, the network can only supportup to 1.14 kilometers (km) of round trip time distance in backhaullinks. Conversely, if the network configures RACH preamble format C2(e.g., with 4 repetitions and a 8.33 μs cyclic prefix duration with 120kHz SCS) in order to meet a 2.5 km round trip time distance in backhaullinks, the network loses approximately 5 decibels (dB) in access RACHlink budget. In other words, if access links and backhaul links are touse the same time-frequency resources for RACH transmissions, thenetwork has to trade-off between supporting higher distance in backhaullinks and higher gain in access links.

Due to the above issues, a NR IAB network may be designed to supportconfiguring access RACH occasions differently from backhaul RACHoccasions (e.g., such that access RACH occasions and backhaul RACHoccasions use different time-frequency resources). Here, a RACH occasiondenotes a set of time-frequency resources for RACH transmissions, and agiven set of time-frequency resources may be for contention based RACHor contention free RACH.

Notably, the capability to differently configure access RACH occasionsand backhaul RACH occasions may require additional signaling by a givenbase station, while the given base station also needs to configureother/additional RACH occasions for backhaul RACH. However, since agiven IAB node requiring a backhaul connection (e.g., a base station)will be relatively static (i.e., have low mobility) in most cases,configuration of contention based backhaul RACH occasions as frequentlyas contention based access RACH occasions may result in wasted networkresources (e.g., since contention based backhaul RACH transmissions maybe occurring less frequently). Hence, it may be advantageous for the IABnetwork to configure contention-based backhaul RACH occasions moreinfrequently than contention-based access RACH occasions.

Some aspects described herein describe identifying a scaling factorassociated with determining a periodicity of backhaul physical RACH(PRACH) resources, and identifying the periodicity of the backhaul PRACHresources based at least in part on the scaling factor. In some aspects,the periodicity of the backhaul PRACH resources is extended as comparedto a periodicity of access PRACH resources, as described below.

Further, a node in an IAB network cannot transmit PRACH to a parent nodeof the IAB node simultaneously with receiving RACH from a child node ofthe IAB node. Additionally, the PRACH resources among adjacent hopsshould be orthogonalized (e.g., in order to prevent the same set ofresources from being used for communications with the parent node andthe child node). However, this reduces flexibility of the IAB network toselect PRACH configuration indices. For example, a pair of configurationindices that identify the same slot number for PRACH resources (e.g., apair of configuration indices with overlapping PRACH resource slots) maynot be selected in adjacent IAB network hops.

Some aspects described herein describe an IAB network configured toexplicitly configure a system frame number (SFN) periodicity and a timeoffset of RACH resources of IAB nodes in order to orthogonalize RACHresources across adjacent IAB network hops.

FIG. 7 is a diagram illustrating an example 700 of determining aperiodicity of backhaul physical RACH (PRACH) resources based at leastin part on a scaling factor, and determining a time offset of thebackhaul PRACH resources, in accordance with various aspects of thepresent disclosure. A new base station and/or a target base station, asdescribed in association with FIG. 7, may each correspond to arespective base station 110, non-anchor base station 545, non-anchorbase station 620/630/640, and/or the like. In some aspects, the new basestation operates with a UE functionality (UEF). A wireless communicationdevice that operates with UEF is herein referred to as a UEF entity. Forexample, the new base station may be used in a mobile termination (MT)of an IAB node (e.g., the new base station may be a scheduled entity forUE/MT of IAB). In some aspects, the target base station operates with anaccess node functionality (ANF). A wireless communication device thatoperates with ANF is herein referred to as an ANF entity. For example,the target base station may be a scheduler for a base station 110.

As noted in FIG. 7, the target base station is deployed within awireless backhaul network (e.g., an IAB network), while the new basestation is a base station that is being deployed in the wirelessbackhaul network (e.g., a base station that is not presently connectedto the wireless backhaul network). For the purposes of example 700,assume that the new base station is to identify a set of backhaul PRACHresources in which to transmit a random access message (e.g., MSG1) forinitiating a RACH procedure associated with establishing a connection,via a wireless backhaul link, with the target base station.

As shown by reference number 705, the new base station may determine ascaling factor and/or a time offset. The scaling factor may include avalue (e.g., an integer value) based at least in part on which aperiodicity of backhaul PRACH resources can be determined. In someaspects, the periodicity of the backhaul PRACH resources, to bedetermined by the new base station, is extended as compared to aperiodicity of access PRACH resources, as described herein.

The time offset includes a time offset of PRACH resources. In someaspects, the IAB network (e.g., the target base station or anotherwireless communication device associated with the IAB network) may(e.g., explicitly) configure the time offset of the backhaul PRACHresources, and may transmit information that identifies the time offsetto the new base station, as indicated in FIG. 7. In some aspects, thetime offset may be identified in terms of a number of radio frames, anumber of slots, a number of subframes, a number of symbols, and/or thelike. In some aspects, the time offset may be different from an timeoffset associated with a PRACH configuration index. In such a case, thetime offset overrides the time offset that is associated with the PRACHconfiguration index, as described below.

In some aspects, as indicated in FIG. 7, the new base station maydetermine the scaling factor and/or the time offset based at least inpart on the scaling factor and/or the time offset, respectively, beingsignaled to the new base station (e.g., by the target base station). Insome aspects, the scaling factor and/or the time offset may be signaledto the new base station via remaining minimum system information (RMSI),other system information (OSI), downlink control information (DCI), amedium access control (MAC) control element (MAC-CE), radio resourcecontrol (RRC) signaling, a handover command, and/or the like.

In some aspects, the scaling factor may be a fixed value. For example,in some aspects, the scaling factor may be defined in a specificationassociated with the IAB network, and this fixed value scaling factor maybe configured on the new base station in accordance with thespecification (e.g., such that information that identifies the scalingfactor is stored or accessible by the new base station, without a needfor the scaling factor to be signaled by the target base station).

As further shown in FIG. 7, and by reference number 710, the new basestation may determine the periodicity of the backhaul PRACH resourcesbased at least in part on the scaling factor.

In some aspects, the periodicity of the backhaul PRACH resources isassociated with identifying a radio frame location of a set of backhaulPRACH resources (e.g., a set of resources that may be used by the newbase station in order to transmit a backhaul RACH transmission).

In some aspects, the new base station may determine the periodicity ofthe backhaul PRACH resources based on a PRACH configuration index. Forexample, the new base station may determine a PRACH configuration indexbased at least in part on information carried in a system informationblock (e.g., SIB2) received by the new base station. The new basestation may then determine (e.g., based on a PRACH configuration indextable configured on the new base station) a periodicity of PRACHresources that corresponds to the PRACH configuration index. Here, thenew base station may determine the periodicity of the backhaul PRACHresources based at least in part on applying the scaling factor to theperiodicity of PRACH resources that corresponds to the PRACHconfiguration index.

As a particular example, assume that the new base station determines ascaling factor 8 and is signaled a PRACH configuration index thatindicates that a PRACH resource periodicity of 16 (e.g., indicating thatPRACH resources occur every 16 radio frames). Here, the new base stationmay determine the periodicity of the backhaul PRACH resources based onmultiplying the scaling factor and the periodicity identified by thePRACH configuration index. Thus, in this example, the new base stationmay determine that backhaul PRACH resources occur every 128 radio frames(e.g., 8×16=128). The new base station may determine particularlocations of the backhaul PRACH resources, within a given radio frame,based at least in part on other information associated with the PRACHconfiguration index. Notably, as illustrated here, the periodicity ofthe backhaul RACH resources (e.g., occurring in every 128 radio frames)is extended as compared to the periodicity of access RACH resources(e.g., when the periodicity of access PRACH resources is to match theperiodicity indicated by the PRACH configuration index). In this way,the scaling factor may be used to extend the periodicity of backhaulPRACH resources through signaling of a single value (i.e., the scalingfactor), thereby reducing signaling overhead and without a need toreconfigure and/or redesign a PRACH configuration index table, whilestill allowing for differently configured backhaul PRACH resources.

In some aspects, the periodicity of the backhaul PRACH resources isassociated with repetition of a mapping pattern that associatessynchronization signal blocks with PRACH resources. For example, theperiodicity may identify an interval of time at which a mapping pattern,associating synchronization signal blocks with respective PRACHresources, is to repeat. In some aspects, the interval of time at whichthe mapping pattern is to repeat may be determined based at least inpart on the scaling factor and a PRACH configuration period, asdescribed below.

Generally, mapping synchronization signal blocks to PRACH resources isneeded in order to allow a wireless communication device (e.g., a UE, anew base station) to indicate a synchronization signal block preferredby the wireless communication device. For example, a givensynchronization signal block may correspond to a particular base stationbeam. Thus, by transmitting the RACH transmission (e.g., MSG1) inparticular RACH resources that map to a preferred synchronization signalblock, the wireless communication device indicates a base station beamto the target base station (e.g., such that the target base station cantransmit a random access response (MSG2) using the indicated beam).However, the mapping pattern associated with mapping synchronizationsignal blocks to PRACH resources should repeat with an identifiableperiodicity. Otherwise, the wireless communication device will be unableto determine which synchronization signal blocks are associated withparticular PRACH resources and, thus, would be unable to indicate apreferred synchronization signal block.

Typically, the mapping pattern should repeat after an associationperiod. The association period is equal to a PRACH configuration periodmultiplied by an integer number (e.g., a value that identifies a numberof PRACH configuration periods). The association period used is equal toa minimum value, of a set of values, that satisfies a full mapping fortransmitted synchronization signal blocks. For example, assume that aPRACH configuration period is 10 milliseconds (ms) and the set ofpossible values includes 1, 2, 4, 8, and 16. Here, the synchronizationsignal block to PRACH resource mapping pattern may repeat after every 10ms (e.g., 10 ms×1=10 ms), every 20 ms (e.g., 10 ms×2=20 ms), every 40 ms(e.g., 10 ms×4=40 ms), every 80 ms (e.g., 10 ms×8=80 ms), or every 160ms (e.g., 10 ms×16=160 ms). The repetition period for the mappingpattern may be selected as the minimum of these five durations thatallows a full set of synchronization signal blocks to be mapped torespective PRACH resources. For example, assume the target base stationtransmits 32 synchronization signal blocks, and that 9 PRACH resourcesare configured within a given 10 ms PRACH configuration period. Thus, 9PRACH resources are configured within 10 ms (e.g., one PRACHconfiguration period), 18 PRACH resources are configured within 20 ms(e.g., two PRACH configuration periods), and 36 PRACH resources areconfigured within 40 ms (e.g., four PRACH configuration periods). Assuch, a full synchronization signal block to PRACH resource mappingrequires at least a four PRACH configuration periods, indicating thatthe mapping pattern should repeat after every 40 ms. Hence, theassociation period in this case is 40 ms.

In the case of backhaul PRACH resources, the repetition of the mappingpattern may be determined based at least in part on the scaling factor.For example, the new base station may determine the repetition of themapping pattern (e.g., an interval at which the mapping pattern is torepeat) based at least in part on the scaling factor, a PRACHconfiguration period, and an integer value. For example, the new basestation may determine the interval at which the mapping pattern is torepeat as an amount of time equal to a product of the scaling factor,the PRACH configuration period, and the integer value.

In some aspects, the repetition of the mapping pattern may be determinedin accordance with the following table:

PRACH configuration Association period (number of period (ms) PRACHconfiguration periods) 10 {1, 2, 4, 8, 16} × S 20 {1, 2, 4, 8} × S 40{1, 2, 4} × S 80 {1, 2} × S 160 {1} × Swhere S represents the scaling factor by which the product of the PRACHconfiguration period and a given integer value is multiplied.

As a particular example, assume that the new base station determines ascaling factor of 4, a PRACH configuration period of 20 ms, and a set ofinteger values including 1, 2, 4, and 8. Here, the new base station maydetermine that the synchronization signal block to PRACH resourcemapping pattern may repeat every 80 ms (e.g., 20 ms×1×4=80 ms), every160 ms (e.g., 20 ms×2×4=160 ms), every 320 ms (e.g., 20 ms×4×4=320 ms),or every 640 ms (e.g., 20 ms×8×4=640 ms). Here, the repetition periodfor the mapping pattern may be selected as the minimum of these fivedurations that allows a full set of synchronization signal blocks to bemapped to respective backhaul PRACH resources, as described above.

In some aspects, since RACH resources may get invalidated due to thepresence of synchronization signal blocks or downlink resources, theassociation period may change over time. For example, during a firsttime period (e.g., from 0 ms to 40 ms) the association period might be40 ms. However, during a second time period (e.g., from 40 ms to 80 ms),the association period can be, for example, equal to 10 ms or 20 ms. Inorder to reduce complexity arising from the irregularity of theassociation period over time, an “association pattern period” may beconfigured. The association pattern period is a period after which thesynchronization signal block to RACH mapping is guaranteed to repeat,irrespective of how RACH resources get invalidated. In some aspects, theassociation pattern period may be equal to 160 ms in an access network.

In some aspects, the new base station may be configured such that themapping pattern is guaranteed to repeat after an amount of time equal toa product of a fixed time value, configured on the new base station, andthe scaling factor. In some aspects, the fixed time value may be, forexample, 160 ms. Thus, in some aspects, the new base station may beconfigured such that the association pattern repeats (at most) every160×S ms, where S represents the scaling factor. Hence, the associationpattern period might 160×S ms in backhaul networks.

Thus, in some aspects, the association period and/or the associationpattern period, associated with mapping synchronization signal blocks toPRACH resources, may be determined based at least in part on the scalingfactor. For example, in some aspects, the association period may bedetermined such that a pattern between PRACH occasions andsynchronization signal blocks repeats at an amount of time that is equalto or less than a product of a PRACH configuration period and thescaling factor. As another example, in some aspects, the associationpattern period may be determined based at least in part on the scalingfactor, a PRACH configuration period associated with the associationperiod, and an integer value associated with the association period.

In this way, the scaling factor may be used to extend the periodicity ofsynchronization signal block to PRACH resource mapping pattern throughsignaling of a single value (i.e., the scaling factor), thereby reducingsignaling overhead while still allowing for differently configuredbackhaul PRACH resources.

As further shown by reference number 710, the new base station maydetermine the time offset of the backhaul PRACH resources. For example,the new base station may determine the time offset based at least inpart on receiving the information that identifies the time offset fromthe target base station. In some aspects, the time offset may be in arange from zero to the periodicity of the backhaul PRACH resources. Insome aspects, the time offset can be configured by the target basestation or another wireless communication device associated with the IABnetwork, as described above. In some aspects, the time offset may beidentified in terms of a number of radio frames, a number of slots, anumber of subframes, a number of symbols, and/or the like. For example,the time offset may include a subframe level offset, such as a subframelevel offset in a range from 0 to 127. As another example, the timeoffset may include a slot level offset, such as a slot level offset in arange from 0 to 39 (e.g., when slot indexing is defined in terms of 60kHz numerology), or a range from 0 to 9 (e.g., when slot indexing isdefined in terms of 15 kHz numerology). In some aspects, the time offsetis used to time division multiplex random access channel (RACH)resources across adjacent hops of a backhaul network.

In some aspects, the time offset may be different from an time offsetthat is identified based at least in part on a PRACH configurationindex. For example, the new base station may determine a PRACHconfiguration index based at least in part on information carried in asystem information block (e.g., SIB2) received by the new base station,as described above. Here, the time offset determined by the new basestation (e.g., based on being signaled by the target base station) maybe different from an time offset identified based at least in part onthe PRACH configuration index (e.g., an time offset identified based atleast in part on the PRACH configuration index table). In some aspects,the time offset may override the time offset that is identified based atleast in part on the PRACH configuration index.

As shown by reference number 715, the new base station may identify aset of backhaul PRACH resources based at least in part on theperiodicity of the backhaul PRACH resources and/or based at least inpart on the time offset. For example, the new base station may, based atleast in part on the periodicity and the time offset, identify a radioframe location of a particular set of backhaul PRACH resources that,according to the mapping pattern, correspond to a particularsynchronization signal block. As shown by reference number 720, the newbase station may then transmit a RACH transmission (e.g., MSG1) usingthe set of identified backhaul PRACH resources.

As indicated above, FIG. 7 is provided as an example. Other examples arepossible and may differ from what was described with respect to FIG. 7.

FIG. 8 is a diagram illustrating an example process 800 performed, forexample, by a UEF entity, in accordance with various aspects of thepresent disclosure. Example process 800 is an example where a UEF entity(e.g., base station 110 with UEF, UE 120) determines, based at least inpart on a scaling factor, a periodicity of a backhaul PRACH resources,wherein the periodicity of the backhaul PRACH resources is extended ascompared to a periodicity of access PRACH resources.

As shown in FIG. 8, in some aspects, process 800 may include identifyinga scaling factor associated with determining a periodicity of backhaulphysical random access channel (PRACH) resources (block 810). Forexample, the UEF entity (e.g., using transmit processor 220/264,controller/processor 240/280, and/or the like), may identify a scalingfactor associated with determining a periodicity of backhaul PRACHresources, as described above.

As shown in FIG. 8, in some aspects, process 800 may includedetermining, based at least in part on the scaling factor, theperiodicity of the backhaul PRACH resources, wherein the periodicity ofthe backhaul PRACH resources is extended as compared to a periodicity ofaccess PRACH resources (block 820). For example, the UEF entity (e.g.,using transmit processor 220/264, controller/processor 240/280, and/orthe like), may determine, based at least in part on the scaling factor,the periodicity of the backhaul PRACH resources, wherein the periodicityof the backhaul PRACH resources is extended as compared to a periodicityof access PRACH resources, as described above.

Process 800 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

Process 800 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In a first aspect, the periodicity of the backhaul PRACH resources isassociated with identifying a radio frame location of a set of backhaulPRACH resources.

In a second aspect, alone or in combination with the first aspect, theperiodicity of the backhaul PRACH resources is determined based at leastin part on the scaling factor and a PRACH configuration index.

In a third aspect, alone or in combination with one or more of the firstand second aspects, the periodicity of the backhaul PRACH resources isdetermined based at least in part on multiplying the scaling factor anda periodicity of PRACH resources associated with the PRACH configurationindex.

In a fourth aspect, alone or in combination with one or more of thefirst through third aspects, the PRACH resources associated with thePRACH configuration index are applicable for PRACH transmission in anaccess network.

In a fifth aspect, alone or in combination with one or more of the firstthrough fourth aspects, a range of the scaling factor is based at leastin part on the periodicity of the PRACH resources associated with thePRACH configuration index.

In a sixth aspect, alone or in combination with one or more of the firstthrough fifth aspects, an association period, associated with mappingsynchronization signal blocks to PRACH resources, is determined based atleast in part on the scaling factor.

In a seventh aspect, alone or in combination with one or more of thefirst through sixth aspects, the association period is determined suchthat a pattern between PRACH occasions and synchronization signal blocksrepeats at an amount of time that is equal to or less than a product ofa PRACH configuration period and the scaling factor.

In an eighth aspect, alone or in combination with one or more of thefirst through seventh aspects, an association pattern period, associatedwith mapping synchronization signal blocks to PRACH resources, isdetermined based at least in part on the scaling factor.

In a ninth aspect, alone or in combination with one or more of the firstthrough eighth aspects, the association pattern period is determinedbased at least in part on the scaling factor, a PRACH configurationperiod associated with an association period, and an integer valueassociated with the association period.

In a tenth aspect, alone or in combination with one or more of the firstthrough ninth aspects, the association pattern period is determined suchthat a pattern between PRACH occasions and synchronization signal blocksrepeats at an amount of time that is equal to or less than a product ofa fixed time value and the scaling factor.

In an eleventh aspect, alone or in combination with one or more of thefirst through tenth aspects, the fixed time value is 160 milliseconds.

In a twelfth aspect, alone or in combination with one or more of thefirst through eleventh aspects, the scaling factor is signaled to theUEF entity via at least one of: remaining minimum system information;other system information; downlink control information; a medium accesscontrol (MAC) control element; radio resource control signaling; or ahandover command.

In a thirteenth aspect, alone or in combination with one or more of thefirst through twelfth aspects, the scaling factor is used in associationwith orthogonalizing RACH occasions across adjacent hops of a backhaulnetwork.

Although FIG. 8 shows example blocks of process 800, in some aspects,process 800 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 8.Additionally, or alternatively, two or more of the blocks of process 800may be performed in parallel.

FIG. 9 is a diagram illustrating an example process 900 performed, forexample, by an access node functionality (ANF) entity, in accordancewith various aspects of the present disclosure. Example process 1000 isan example where an ANF entity (e.g., base station 110 with ANF) signalsa scaling factor, associated with determining a periodicity of abackhaul PRACH resources, wherein the periodicity of the backhaul PRACHresources is to be extended as compared to a periodicity of access PRACHresources.

As shown in FIG. 9, in some aspects, process 900 identifying a scalingfactor to be used by a user equipment functionality (UEF) entity inassociation with determining a periodicity of backhaul physical randomaccess channel (PRACH) resources (block 910). For example, the ANFentity (e.g., using controller/processor 240, and/or the like), mayidentify a scaling factor to be used by a UEF entity (e.g., a basestation 110 with UEF) in association with determining a periodicity ofbackhaul PRACH resources, as described above. In some aspects, theperiodicity of the backhaul PRACH resources is to be extended ascompared to a periodicity of access PRACH resources.

As further shown in FIG. 9, in some aspects, process 900 may includesignaling the scaling factor to the UEF entity (block 920). For example,the ANF entity (e.g., using transmit processor 220, controller/processor240, and/or the like) may signal the scaling factor to the UEF entity,as described above.

Process 900 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In a first aspect, the periodicity of the backhaul PRACH resources isassociated with identifying a radio frame location of a set of backhaulPRACH resources.

In a second aspect, alone or in combination with the first aspect, theperiodicity of the backhaul PRACH resources is to be determined based atleast in part on the scaling factor and a PRACH configuration index.

In a third aspect, alone or in combination with one or more of the firstand second aspects, the periodicity of the backhaul PRACH resources isto be determined based at least in part on multiplying the scalingfactor and a periodicity of PRACH resources associated with the PRACHconfiguration index.

In a fourth aspect, alone or in combination with one or more of thefirst through third aspects, the PRACH resources associated with thePRACH configuration index are applicable for PRACH transmission in anaccess network.

In a fifth aspect, alone or in combination with one or more of the firstthrough fourth aspects, a range of the scaling factor is based at leastin part on the periodicity of the PRACH resources associated with thePRACH configuration index.

In a sixth aspect, alone or in combination with one or more of the firstthrough fifth aspects, an association period, associated with mappingsynchronization signal blocks to PRACH resources, is determined based atleast in part on the scaling factor.

In a seventh aspect, alone or in combination with one or more of thefirst through sixth aspects, the association period is determined suchthat a pattern between PRACH occasions and synchronization signal blocksrepeats at an amount of time that is equal to or less than a product ofa PRACH configuration period and the scaling factor.

In an eighth aspect, alone or in combination with one or more of thefirst through seventh aspects, an association pattern period, associatedwith mapping synchronization signal blocks to PRACH resources, is to bedetermined based at least in part on the scaling factor.

In a ninth aspect, alone or in combination with one or more of the firstthrough eighth aspects, the association pattern period is to bedetermined based at least in part on the scaling factor, a PRACHconfiguration period associated with an association period, and aninteger value associated with the association period.

In a tenth aspect, alone or in combination with one or more of the firstthrough ninth aspects, the association pattern period is to bedetermined such that a pattern between PRACH occasions andsynchronization signal blocks repeats at an amount of time that is equalto or less than a product of a fixed time value and the scaling factor.

In an eleventh aspect, alone or in combination with one or more of thefirst through tenth aspects, the fixed time value is 160 milliseconds.

In a twelfth aspect, alone or in combination with one or more of thefirst through eleventh aspects, the scaling factor is signaled to theUEF entity via at least one of: remaining minimum system information;other system information; downlink control information; a medium accesscontrol (MAC) control element; radio resource control signaling; or ahandover command.

In a thirteenth aspect, alone or in combination with one or more of thefirst through twelfth aspects, the scaling factor is used in associationwith orthogonalizing RACH occasions across adjacent hops of a backhaulnetwork.

FIG. 10 is a diagram illustrating an example process 1000 performed, forexample, by an ANF entity, in accordance with various aspects of thepresent disclosure. Example process 1000 is an example where a wirelesscommunication device (e.g., base station 110 with ANF) configures a timeoffset of backhaul PRACH resources, and transmits information thatidentifies the time offset.

As shown in FIG. 10, in some aspects, process 1000 may includeconfiguring a time offset of backhaul PRACH resources (block 1010). Forexample, the wireless communication device (e.g., usingcontroller/processor 240, and/or the like), may configure a time offsetof backhaul PRACH resources, as described above.

As shown in FIG. 10, in some aspects, process 1000 may includetransmitting information that identifies the time offset (block 1020).For example, the wireless communication device (e.g., using antenna 234,transmit processor 220, controller/processor 240, and/or the like), maytransmit information that identifies the time offset, as describedabove. In some aspects, the time offset may be different from a timeoffset that is identified based at least in part on a PRACHconfiguration index

Process 1000 may include additional aspects, such as any single aspector any combination of aspects described below and/or in connection withone or more other processes described elsewhere herein.

In a first aspect, the time offset includes a subframe level offset.

In a second aspect, alone or in combination with the first aspect, thesubframe level offset is in a range from 0 to 127.

In a third aspect, alone or in combination with one or more of the firstand second aspects, the time offset includes a slot level offset.

In a fourth aspect, alone or in combination with one or more of thefirst through third aspects, the slot level offset is in a range from 0to 39.

In a fifth aspect, alone or in combination with one or more of the firstthrough fourth aspects, the slot indexing is defined in terms of 60kilohertz (kHz) numerology.

In a sixth aspect, alone or in combination with one or more of the firstthrough fifth aspects, the slot level offset is in a range from 0 to 9.

In a seventh aspect, alone or in combination with one or more of thefirst through sixth aspects, the slot indexing is defined in terms of 15kilohertz (kHz) numerology.

In an eighth aspect, alone or in combination with one or more of thefirst through seventh aspects, the time offset is used to time divisionmultiplex random access channel (RACH) resources across adjacent hops ofa backhaul network.

In a ninth aspect, alone or in combination with one or more of the firstthrough eighth aspects, the time offset is signaled via at least one of:remaining minimum system information; other system information; downlinkcontrol information; a medium access control (MAC) control element;radio resource control signaling; or a handover command.

In a tenth aspect, alone or in combination with one or more of the firstthrough ninth aspects, the time offset is used in association withorthogonalizing RACH occasions across adjacent hops of a backhaulnetwork.

In an eleventh aspect, alone or in combination with one or more of thefirst through tenth aspects, the time offset is in a range from zero toa periodicity of the backhaul PRACH resources.

In a twelfth aspect, alone or in combination with one or more of thefirst through eleventh aspects, the time offset overrides the timeoffset that is identified based at least in part on the PRACHconfiguration index.

Although FIG. 10 shows example blocks of process 1000, in some aspects,process 1000 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 10.Additionally, or alternatively, two or more of the blocks of process1000 may be performed in parallel.

FIG. 11 is a diagram illustrating an example process 1100 performed, forexample, by a UEF entity, in accordance with various aspects of thepresent disclosure. Example process 1100 is an example where a UEFentity (e.g., base station 110 with UEF, UE 120) identifies a set ofbackhaul PRACH resources based at least in part on a time offset andtransmits a RACH transmission using the identified set of PRACHresources.

As shown in FIG. 11, in some aspects, process 1100 may include receivinginformation that identifies a time offset associated with backhaul PRACHresources (block 1110). For example, the UEF entity (e.g., using antenna234/252, receive processor 238/258, controller/processor 240/280, and/orthe like), receiving information that identifies a time offsetassociated with backhaul PRACH resources, as described above. In someaspects, the time offset may be different from a time offset that isidentified based at least in part on a PRACH configuration index

As shown in FIG. 11, in some aspects, process 1100 may includeidentifying a set of backhaul PRACH resources based at least in part onthe time offset (block 1120). For example, the UEF entity (e.g., usingcontroller/processor 240/280, and/or the like), may identify a set ofbackhaul PRACH resources based at least in part on the time offset, asdescribed above.

As shown in FIG. 11, in some aspects, process 1100 may includetransmitting a RACH transmission using the identified set of backbackhaul PRACH resources (block 1130). For example, the UEF entity(e.g., using antenna 234/252, transmit processor 220/264,controller/processor 240/280, and/or the like), may transmit a RACHtransmission using the identified set of back backhaul PRACH resources.,as described above.

Process 1100 may include additional aspects, such as any single aspector any combination of aspects described below and/or in connection withone or more other processes described elsewhere herein.

In a first aspect, the time offset includes a subframe level offset.

In a second aspect, alone or in combination with the first aspect, thesubframe level offset is in a range from 0 to 127.

In a third aspect, alone or in combination with one or more of the firstand second aspects, the time offset includes a slot level offset.

In a fourth aspect, alone or in combination with one or more of thefirst through third aspects, the slot level offset is in a range from 0to 39.

In a fifth aspect, alone or in combination with one or more of the firstthrough fourth aspects, the slot indexing is defined in terms of 60kilohertz (kHz) numerology.

In a sixth aspect, alone or in combination with one or more of the firstthrough fifth aspects, the slot level offset is in a range from 0 to 9.

In a seventh aspect, alone or in combination with one or more of thefirst through sixth aspects, the slot indexing is defined in terms of 15kilohertz (kHz) numerology.

In an eighth aspect, alone or in combination with one or more of thefirst through seventh aspects, the time offset is used to time divisionmultiplex random access channel (RACH) resources across adjacent hops ofa backhaul network.

In a ninth aspect, alone or in combination with one or more of the firstthrough eighth aspects, the time offset is signaled to the UEF entityvia at least one of: remaining minimum system information; other systeminformation; downlink control information; a medium access control (MAC)control element; radio resource control signaling; or a handovercommand.

In a tenth aspect, alone or in combination with one or more of the firstthrough ninth aspects, the time offset is used in association withorthogonalizing RACH occasions across adjacent hops of a backhaulnetwork.

In an eleventh aspect, alone or in combination with one or more of thefirst through tenth aspects, the time offset is in a range from zero toa periodicity of the backhaul PRACH resources.

In a twelfth aspect, alone or in combination with one or more of thefirst through eleventh aspects, the time offset overrides the timeoffset that is identified based at least in part on the PRACHconfiguration index.

Although FIG. 11 shows example blocks of process 1100, in some aspects,process 1100 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 11.Additionally, or alternatively, two or more of the blocks of process1100 may be performed in parallel.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the aspects to the preciseform disclosed. Modifications and variations are possible in light ofthe above disclosure or may be acquired from practice of the aspects.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software. Asused herein, a processor is implemented in hardware, firmware, or acombination of hardware and software.

Some aspects are described herein in connection with thresholds. As usedherein, satisfying a threshold may refer to a value being greater thanthe threshold, greater than or equal to the threshold, less than thethreshold, less than or equal to the threshold, equal to the threshold,not equal to the threshold, and/or the like.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the aspects. Thus, the operation and behavior of thesystems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based, at leastin part, on the description herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible aspects. In fact, many ofthese features may be combined in ways not specifically recited in theclaims and/or disclosed in the specification. Although each dependentclaim listed below may directly depend on only one claim, the disclosureof possible aspects includes each dependent claim in combination withevery other claim in the claim set. A phrase referring to “at least oneof” a list of items refers to any combination of those items, includingsingle members. As an example, “at least one of: a, b, or c” is intendedto cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combinationwith multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c,a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering ofa, b, and c).

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the terms “set” and “group” are intended to include oneor more items (e.g., related items, unrelated items, a combination ofrelated and unrelated items, and/or the like), and may be usedinterchangeably with “one or more.” Where only one item is intended, theterm “one” or similar language is used. Also, as used herein, the terms“has,” “have,” “having,” and/or the like are intended to be open-endedterms. Further, the phrase “based on” is intended to mean “based, atleast in part, on” unless explicitly stated otherwise.

What is claimed is:
 1. A method of wireless communication performed by auser equipment functionality (UEF) entity, comprising: identifying ascaling factor associated with determining a periodicity of backhaulphysical random access channel (PRACH) resources; and determining, basedat least in part on the scaling factor, the periodicity of the backhaulPRACH resources, wherein the periodicity of the backhaul PRACH resourcesis extended as compared to a periodicity of access PRACH resources. 2.The method of claim 1, wherein the periodicity of the backhaul PRACHresources is associated with identifying a radio frame location of a setof backhaul PRACH resources.
 3. The method of claim 1, wherein theperiodicity of the backhaul PRACH resources is determined based at leastin part on the scaling factor and a PRACH configuration index.
 4. Themethod of claim 3, wherein the periodicity of the backhaul PRACHresources is determined based at least in part on multiplying thescaling factor and a periodicity of PRACH resources associated with thePRACH configuration index.
 5. The method of claim 4, wherein the PRACHresources associated with the PRACH configuration index are applicablefor PRACH transmission in an access network.
 6. The method of claim 4,wherein a range of the scaling factor is based at least in part on theperiodicity of the PRACH resources associated with the PRACHconfiguration index.
 7. The method of claim 1, wherein an associationperiod, associated with mapping synchronization signal blocks to PRACHresources, is determined based at least in part on the scaling factor.8. The method of claim 7, wherein the association period is determinedsuch that a pattern between PRACH occasions and synchronization signalblocks repeats at an amount of time that is equal to or less than aproduct of a PRACH configuration period and the scaling factor.
 9. Themethod of claim 1, wherein an association pattern period, associatedwith mapping synchronization signal blocks to PRACH resources, isdetermined based at least in part on the scaling factor.
 10. The methodof claim 9, wherein the association pattern period is determined basedat least in part on the scaling factor, a PRACH configuration periodassociated with an association period, and an integer value associatedwith the association period.
 11. The method of claim 9, wherein theassociation pattern period is determined such that a pattern betweenPRACH occasions and synchronization signal blocks repeats at an amountof time that is equal to or less than a product of a fixed time valueand the scaling factor.
 12. The method of claim 11, wherein the fixedtime value is 160 milliseconds.
 13. The method of claim 1, wherein thescaling factor is signaled to the UEF entity via at least one of:remaining minimum system information; other system information; downlinkcontrol information; a medium access control (MAC) control element;radio resource control signaling; or a handover command.
 14. The methodof claim 1, wherein the scaling factor is used in association withorthogonalizing RACH occasions across adjacent hops of a backhaulnetwork.
 15. A user equipment functionality (UEF) entity for wirelesscommunication comprising: memory; and one or more processors operativelycoupled to the memory, the memory and the one or more processorsconfigured to: identify a scaling factor associated with determining aperiodicity of backhaul physical random access channel (PRACH)resources; and determine, based at least in part on the scaling factor,the periodicity of the backhaul PRACH resources, wherein the periodicityof the backhaul PRACH resources is extended as compared to a periodicityof access PRACH resources.
 16. A method of wireless communicationperformed by an access node functionality (ANF) entity, comprising:identifying a scaling factor to be used by a user equipmentfunctionality (UEF) entity in association with determining a periodicityof backhaul physical random access channel (PRACH) resources, whereinthe periodicity of the backhaul PRACH resources is to be extended ascompared to a periodicity of access PRACH resources; and signaling thescaling factor to the UEF entity.
 17. The method of claim 16, whereinthe periodicity of the backhaul PRACH resources is associated withidentifying a radio frame location of a set of backhaul PRACH resources.18. The method of claim 16, wherein the periodicity of the backhaulPRACH resources is to be determined based at least in part on thescaling factor and a PRACH configuration index.
 19. The method of claim18, wherein the periodicity of the backhaul PRACH resources is to bedetermined based at least in part on multiplying the scaling factor anda periodicity of PRACH resources associated with the PRACH configurationindex.
 20. The method of claim 19, wherein the PRACH resourcesassociated with the PRACH configuration index are applicable for PRACHtransmission in an access network.
 21. The method of claim 19, wherein arange of the scaling factor is based at least in part on the periodicityof the PRACH resources associated with the PRACH configuration index.22. The method of claim 16, wherein an association period, associatedwith mapping synchronization signal blocks to PRACH resources, isdetermined based at least in part on the scaling factor.
 23. The methodof claim 22, wherein the association period is determined such that apattern between PRACH occasions and synchronization signal blocksrepeats at an amount of time that is equal to or less than a product ofa PRACH configuration period and the scaling factor.
 24. The method ofclaim 16, wherein an association pattern period, associated with mappingsynchronization signal blocks to PRACH resources, is to be determinedbased at least in part on the scaling factor.
 25. The method of claim24, wherein the association pattern period is to be determined based atleast in part on the scaling factor, a PRACH configuration periodassociated with an association period, and an integer value associatedwith the association period.
 26. The method of claim 24, wherein theassociation pattern period is to be determined such that a patternbetween PRACH occasions and synchronization signal blocks repeats at anamount of time that is equal to or less than a product of a fixed timevalue and the scaling factor.
 27. The method of claim 26, wherein thefixed time value is 160 milliseconds.
 28. The method of claim 16,wherein the scaling factor is signaled to the UEF entity via at leastone of: remaining minimum system information; other system information;downlink control information; a medium access control (MAC) controlelement; radio resource control signaling; or a handover command. 29.The method of claim 16, wherein the scaling factor is used inassociation with orthogonalizing RACH occasions across adjacent hops ofa backhaul network.
 30. An access node functionality (ANF) entity forwireless communication comprising: memory; and one or more processorsoperatively coupled to the memory, the memory and the one or moreprocessors configured to: identify a scaling factor to be used by a userequipment functionality (UEF) entity in association with determining aperiodicity of backhaul physical random access channel (PRACH)resources, wherein the periodicity of the backhaul PRACH resources is tobe extended as compared to a periodicity of access PRACH resources; andsignal the scaling factor to the UEF entity.